| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-CPS.9.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | CPS_9_2_Support_for_Inter_Provider_Communication |
| Title | CPS.9.2 Support for Inter-Provider Communication (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Support exchange of information between providers as part of the patient care process, and the appropriate documentation of such exchanges. Support secure communication to protect the privacy of information as required by jurisdictional law. |
| Purpose | Communication among providers involved in the care process can range from real time communication (for example, communication between a therapist and nurse), to asynchronous communication (e.g., consult reports between physicians). Some forms of inter-practitioner communication will be paper based and the EHR-S must be able to produce appropriate documents. The system should provide for both verbal and written communication. These exchanges would include but not be limited to consults, and referrals as well as possible exchanges within the office as part of the provision and administration of patient care (e.g., the communication of new information obtained within the office environment during the process of administration of a tetanus shot while the patient is in the exam room).The system should support the creation and acceptance of paper artifacts where appropriate. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Support exchange of information between providers as part of the patient care process, and the appropriate documentation of such exchanges. Support secure communication to protect the privacy of information as required by jurisdictional law.
Communication among providers involved in the care process can range from real time communication (for example, communication between a therapist and nurse), to asynchronous communication (e.g., consult reports between physicians). Some forms of inter-practitioner communication will be paper based and the EHR-S must be able to produce appropriate documents.
The system should provide for both verbal and written communication. These exchanges would include but not be limited to consults, and referrals as well as possible exchanges within the office as part of the provision and administration of patient care (e.g., the communication of new information obtained within the office environment during the process of administration of a tetanus shot while the patient is in the exam room).The system should support the creation and acceptance of paper artifacts where appropriate.
| CPS.9.2#01 | SHALL |
The system SHALL provide the ability to capture and store in the patient record verbal/telephone communication (including verbal orders) between providers including the identification of these providers. |
| CPS.9.2#02 | SHALL |
The system SHALL provide the ability to integrate scanned documents from providers into the patient record. |
| CPS.9.2#03 | SHOULD |
The system SHOULD provide the ability to receive and transmit messages or information in real time. |
| CPS.9.2#04 | SHOULD |
The system SHOULD provide the ability to receive and transmit clinical information (e.g., referrals) via secure e-mail or other secure standard electronic means. |
| CPS.9.2#05 | SHALL |
The system SHALL provide the ability to transmit (e.g., via e-mail) specific patient data (e.g.reports, results, documents) to alternate providers/facilities in an emergency care context. |
| CPS.9.2#06 | SHOULD |
The system SHOULD provide the ability to transmit specific patient diagnostic quality images (e.g., sound, EKG waveform, EKG graph, video, diagnostic imaging) to alternate providers/facilities in an emergency care context. |
| CPS.9.2#07 | SHOULD |
The system SHOULD provide the ability to receive and transmit in a secure manner electronic multi-media data types representing pictures, sound clips, or video as part of the patient record. |
| CPS.9.2#08 | SHOULD |
The system SHOULD provide the ability for the user to render a patient status (e.g., arrival, admission, discharge, death) notification to providers and care managers (e.g., the Emergency Department physician sends a notification to members of the care team that the patient has been admitted). |
| CPS.9.2#09 | SHOULD |
The system SHOULD provide the ability to render patient status (e.g., arrival, admission, discharge, death) notification to providers and care manager, based on clinical rules (e.g., a rules-engine automatically sends an notification to all members of the care team that the patient has arrived at the hospital). |
| CPS.9.2#10 | MAY |
The system MAY provide the ability for the user to render patient care plans/instructions to providers and care managers when a patient's status has changed. |
| CPS.9.2#11 | MAY |
The system MAY provide the ability to render patient care plans/instructions to providers and care managers based on clinical rules when a patient's status has changed. |
| CPS.9.2#12 | MAY |
The system MAY provide the ability to render an alert to an originating external provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request. |
| CPS.9.2#13 | SHOULD |
The system SHOULD provide the ability to render an alert the originating internal provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-CPS.9.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Support exchange of information between providers as part of the patient care process, and the appropriate documentation of such exchanges. Support secure communication to protect the privacy of information as required by jurisdictional law.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Communication among providers involved in the care process can range from real time communication (for example, communication between a therapist and nurse), to asynchronous communication (e.g., consult reports between physicians). Some forms of inter-practitioner communication will be paper based and the EHR-S must be able to produce appropriate documents.</p>\n<p>The system should provide for both verbal and written communication. These exchanges would include but not be limited to consults, and referrals as well as possible exchanges within the office as part of the provision and administration of patient care (e.g., the communication of new information obtained within the office environment during the process of administration of a tetanus shot while the patient is in the exam room).The system should support the creation and acceptance of paper artifacts where appropriate.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture and store in the patient record verbal/telephone communication (including verbal orders) between providers including the identification of these providers.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to integrate scanned documents from providers into the patient record.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive and transmit messages or information in real time.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive and transmit clinical information (e.g., referrals) via secure e-mail or other secure standard electronic means.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to transmit (e.g., via e-mail) specific patient data (e.g.reports, results, documents) to alternate providers/facilities in an emergency care context.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to transmit specific patient diagnostic quality images (e.g., sound, EKG waveform, EKG graph, video, diagnostic imaging) to alternate providers/facilities in an emergency care context.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to receive and transmit in a secure manner electronic multi-media data types representing pictures, sound clips, or video as part of the patient record.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability for the user to render a patient status (e.g., arrival, admission, discharge, death) notification to providers and care managers (e.g., the Emergency Department physician sends a notification to members of the care team that the patient has been admitted).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render patient status (e.g., arrival, admission, discharge, death) notification to providers and care manager, based on clinical rules (e.g., a rules-engine automatically sends an notification to all members of the care team that the patient has arrived at the hospital).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability for the user to render patient care plans/instructions to providers and care managers when a patient's status has changed.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render patient care plans/instructions to providers and care managers based on clinical rules when a patient's status has changed.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render an alert to an originating external provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>CPS.9.2#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render an alert the originating internal provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-CPS.9.2",
"version" : "2.1.0",
"name" : "CPS_9_2_Support_for_Inter_Provider_Communication",
"title" : "CPS.9.2 Support for Inter-Provider Communication (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Support exchange of information between providers as part of the patient care process, and the appropriate documentation of such exchanges. Support secure communication to protect the privacy of information as required by jurisdictional law.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Communication among providers involved in the care process can range from real time communication (for example, communication between a therapist and nurse), to asynchronous communication (e.g., consult reports between physicians). Some forms of inter-practitioner communication will be paper based and the EHR-S must be able to produce appropriate documents.\n\nThe system should provide for both verbal and written communication. These exchanges would include but not be limited to consults, and referrals as well as possible exchanges within the office as part of the provision and administration of patient care (e.g., the communication of new information obtained within the office environment during the process of administration of a tetanus shot while the patient is in the exam room).The system should support the creation and acceptance of paper artifacts where appropriate.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-01",
"label" : "CPS.9.2#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture and store in the patient record verbal/telephone communication (including verbal orders) between providers including the identification of these providers.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.1#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-02",
"label" : "CPS.9.2#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to integrate scanned documents from providers into the patient record.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.1#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-03",
"label" : "CPS.9.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive and transmit messages or information in real time.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.1#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-04",
"label" : "CPS.9.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive and transmit clinical information (e.g., referrals) via secure e-mail or other secure standard electronic means.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.1#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-05",
"label" : "CPS.9.2#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to transmit (e.g., via e-mail) specific patient data (e.g.reports, results, documents) to alternate providers/facilities in an emergency care context."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-06",
"label" : "CPS.9.2#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit specific patient diagnostic quality images (e.g., sound, EKG waveform, EKG graph, video, diagnostic imaging) to alternate providers/facilities in an emergency care context."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-07",
"label" : "CPS.9.2#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to receive and transmit in a secure manner electronic multi-media data types representing pictures, sound clips, or video as part of the patient record.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.2.1#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-08",
"label" : "CPS.9.2#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability for the user to render a patient status (e.g., arrival, admission, discharge, death) notification to providers and care managers (e.g., the Emergency Department physician sends a notification to members of the care team that the patient has been admitted)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-09",
"label" : "CPS.9.2#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render patient status (e.g., arrival, admission, discharge, death) notification to providers and care manager, based on clinical rules (e.g., a rules-engine automatically sends an notification to all members of the care team that the patient has arrived at the hospital)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-10",
"label" : "CPS.9.2#10",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability for the user to render patient care plans/instructions to providers and care managers when a patient's status has changed."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-11",
"label" : "CPS.9.2#11",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render patient care plans/instructions to providers and care managers based on clinical rules when a patient's status has changed."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-12",
"label" : "CPS.9.2#12",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render an alert to an originating external provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-CPS.9.2-13",
"label" : "CPS.9.2#13",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render an alert the originating internal provider who has submitted information or a request, about the target internal provider's unavailability (e.g., vacations) and recommend rerouting of the information or request."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.